Skip to content

branch-4.0: [fix](be) Default to the Default chain when S3 role_arn is set without provider_type #60822#60965

Merged
yiguolei merged 1 commit intobranch-4.0from
auto-pick-60822-branch-4.0
Mar 3, 2026
Merged

branch-4.0: [fix](be) Default to the Default chain when S3 role_arn is set without provider_type #60822#60965
yiguolei merged 1 commit intobranch-4.0from
auto-pick-60822-branch-4.0

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 2, 2026

Cherry-picked from #60822

…t provider_type (#60822)

closed #60501 

  One-line summary
On the BE side, setting AWS_ROLE_ARN no longer implicitly forces
cred_provider_type to INSTANCE_PROFILE; if AWS_CREDENTIALS_PROVIDER_TYPE
is not explicitly provided, it now defaults to the Default chain.

  Behavior change

  - Before: AWS_ROLE_ARN only -> INSTANCE_PROFILE
  - After: AWS_ROLE_ARN only -> DEFAULT (Default chain)
- Explicit config still wins: AWS_CREDENTIALS_PROVIDER_TYPE=WEB_IDENTITY
-> WEB_IDENTITY
@github-actions github-actions bot requested a review from yiguolei as a code owner March 2, 2026 16:10
@Thearas
Copy link
Contributor

Thearas commented Mar 2, 2026

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Mar 2, 2026
@dataroaring dataroaring reopened this Mar 2, 2026
@Thearas
Copy link
Contributor

Thearas commented Mar 2, 2026

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.99% (19132/36107)
Line Coverage 36.18% (178186/492444)
Region Coverage 32.78% (138046/421167)
Branch Coverage 33.75% (59943/177622)

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Mar 3, 2026
@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 3, 2026

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 3, 2026

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit add05a8 into branch-4.0 Mar 3, 2026
28 of 31 checks passed
@github-actions github-actions bot deleted the auto-pick-60822-branch-4.0 branch March 3, 2026 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants